---
title: 'OTLP gRPC'
description: 'Configuring the OTLP gRPC backend (Self-Hosted)'
sidebarTitle: 'OTLP gRPC'
icon: 'signal-stream'
---

### Getting Started

<img src="https://d15jtxgb40qetw.cloudfront.net/opentelemetry.svg" alt="otlp" className="not-prose h-20" />

{/*
    Add custom content here (under this comment)...

    e.g.

    **Creating Account**<br />
    Go to the **[🔗 website](https://odigos.io) > Account** and click **Sign Up**

    **Obtaining Access Token**<br />
    Go to **⚙️ > Access Tokens** and click **Create New**

    !! Do not remove this comment, this acts as a key indicator in `docs/sync-dest-doc.py` !!
    !! START CUSTOM EDIT !!
*/}

For advanced users trying to implement complex observability pipelines, Odigos support sending data to any OTLP gRPC unencrypted endpoint.

<Note>
  Note that if your backend expects [OTLP over http](https://opentelemetry.io/docs/specs/otel/protocol/exporter/#configuration-options) you should use the [OTLP http](/backends/otlphttp) destination instead.
</Note>

<Tip>
  If your backend is supported natively in Odigos, it's recommended to use the native integration.
</Tip>

{/*
    !! Do not remove this comment, this acts as a key indicator in `docs/sync-dest-doc.py` !!
    !! END CUSTOM EDIT !!
*/}

### Configuring Destination Fields

<Accordion title="Supported Signals:">
  ✅ Traces
  ✅ Metrics
  ✅ Logs
</Accordion>

- **OTLP_GRPC_ENDPOINT** `string` : OTLP gRPC Endpoint. The format is `host:port`, host is required, port is optional and defaults to the default OTLP gRPC port `4317`.
  - This field is required
  - Example: `host:port`
- **OTLP_GRPC_COMPRESSION** `string` : Destination Compression Type. Compression type to use for the destination. The default is `none`. The compression type must be supported by the destination.
  - This field is optional and defaults to `none`
- **OTLP_GRPC_HEADERS** `{ key: string; value: string; }[]` : Headers. Headers is the option to set custom GRPC headers for OTLP GRPC destination. If specified, please provide each header in the format: key:value. Multiple headers can be added. Keys must be non-empty strings and follow standard HTTP header conventions. Values must be non-empty strings and may include alphanumerics, whitespace, and standard punctuation.
  - This field is optional
- **OTLP_GRPC_OAUTH2_ENABLED** `boolean` : Enable OAuth2. Enable OAuth2 client credentials authentication
  - This field is optional and defaults to `False`
- **OTLP_GRPC_OAUTH2_CLIENT_ID** `string` : OAuth2 Client ID. OAuth2 client identifier for client credentials flow
  - This field is optional
  - Example: `your-client-id`
- **OTLP_GRPC_OAUTH2_CLIENT_SECRET** `string` : OAuth2 Client Secret. OAuth2 client secret for client credentials flow
  - This field is optional
  - Example: `your-client-secret`
- **OTLP_GRPC_OAUTH2_TOKEN_URL** `string` : OAuth2 Token URL. OAuth2 token endpoint URL for obtaining access tokens
  - This field is optional
  - Example: `https://example.com/oauth2/token`
- **OTLP_GRPC_OAUTH2_SCOPES** `string` : OAuth2 Scopes. Comma-separated list of OAuth2 scopes to request (e.g., "api.metrics,api.traces")
  - This field is optional
  - Example: `api.metrics,api.traces`
- **OTLP_GRPC_OAUTH2_AUDIENCE** `string` : OAuth2 Audience. OAuth2 audience parameter for token requests
  - This field is optional
  - Example: `api.example.com`
- **OTLP_GRPC_TLS_ENABLED** `boolean` : Enable TLS. Secure connection
  - This field is optional and defaults to `False`
- **OTLP_GRPC_CA_PEM** `string` : Certificate Authority. When using TLS, provide the CA certificate in PEM format to verify the server. If empty uses system root CA
  - This field is optional
  - Example: `-----BEGIN CERTIFICATE-----`
- **OTLP_GRPC_INSECURE_SKIP_VERIFY** `boolean` : Insecure Skip Verify. Skip TLS certificate verification
  - This field is optional and defaults to `False`

### Adding Destination to Odigos

There are two primary methods for configuring destinations in Odigos:

##### **Using the UI**

<Steps>
  <Step>
    Use the [Odigos CLI](https://docs.odigos.io/cli/odigos_ui) to access the UI
    ```bash
    odigos ui
    ```
  </Step>
  <Step>
    Click on `Add Destination`, select `OTLP gRPC` and follow the on-screen instructions
  </Step>
</Steps>

##### **Using Kubernetes manifests**

<Steps>
  <Step>
    Save the YAML below to a file (e.g. `otlp.yaml`)
    ```yaml
    apiVersion: odigos.io/v1alpha1
    kind: Destination
    metadata:
      name: otlp-example
      namespace: odigos-system
    spec:
      data:
        OTLP_GRPC_ENDPOINT: <OTLP gRPC Endpoint>
        # Note: The commented fields below are optional.
        # OTLP_GRPC_COMPRESSION: <Destination Compression Type (default: none) (options: [none, gzip, snappy, lz4, zlib, deflate, zstd])>
        # OTLP_GRPC_HEADERS: <Headers>
        # OTLP_GRPC_OAUTH2_ENABLED: <Enable OAuth2>
        # OTLP_GRPC_OAUTH2_CLIENT_ID: <OAuth2 Client ID>
        # OTLP_GRPC_OAUTH2_TOKEN_URL: <OAuth2 Token URL>
        # OTLP_GRPC_OAUTH2_SCOPES: <OAuth2 Scopes>
        # OTLP_GRPC_OAUTH2_AUDIENCE: <OAuth2 Audience>
        # OTLP_GRPC_TLS_ENABLED: <Enable TLS>
        # OTLP_GRPC_CA_PEM: <Certificate Authority>
        # OTLP_GRPC_INSECURE_SKIP_VERIFY: <Insecure Skip Verify>
      destinationName: otlp
      # Uncomment the 'secretRef' below if you are using the optional Secret.
      # secretRef:
      #   name: otlp-secret
      signals:
      - TRACES
      - METRICS
      - LOGS
      type: otlp

    ---

    # The following Secret is optional. Uncomment the entire block if you need to use it.
    # apiVersion: v1
    # data:
    #   OTLP_GRPC_OAUTH2_CLIENT_SECRET: <Base64 OAuth2 Client Secret>
    # kind: Secret
    # metadata:
    #   name: otlp-secret
    #   namespace: odigos-system
    # type: Opaque
    ```
  </Step>
  <Step>
    Apply the YAML using `kubectl`
    ```bash
    kubectl apply -f otlp.yaml
    ```
  </Step>
</Steps>